HAProxy must be configured with FIPS 140-2 compliant ciphers for https connections.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-240041	VRAU-HA-000015	SV-240041r879519_rule		Medium

Description
Transport Layer Security (TLS) is optional for a public web server. However, if authentication is being performed, then the use of the TLS protocol is required. Without the use of TLS, the authentication data would be transmitted unencrypted and would become vulnerable to disclosure. Using TLS along with DoD PKI certificates for encryption of the authentication data protects the information from being accessed by all parties on the network. To further protect the authentication data, the web server must use a FIPS 140-2 approved TLS version and all non-FIPS-approved SSL versions must be disabled. FIPS 140-2 approved TLS versions include TLS V1.0 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.

Description

Transport Layer Security (TLS) is optional for a public web server. However, if authentication is being performed, then the use of the TLS protocol is required. Without the use of TLS, the authentication data would be transmitted unencrypted and would become vulnerable to disclosure. Using TLS along with DoD PKI certificates for encryption of the authentication data protects the information from being accessed by all parties on the network. To further protect the authentication data, the web server must use a FIPS 140-2 approved TLS version and all non-FIPS-approved SSL versions must be disabled. FIPS 140-2 approved TLS versions include TLS V1.0 or greater. NIST SP 800-52 specifies the preferred configurations for government systems.

STIG	Date
VMW vRealize Automation 7.x HA Proxy Security Technical Implementation Guide	2023-09-12

Details

Check Text ( C-43274r665290_chk )
Navigate to and open the following files: /etc/haproxy/conf.d/20-vcac.cfg /etc/haproxy/conf.d/30-vro-config.cfg Verify that each frontend is configured with the following: bind : ssl crt ciphers FIPS:+3DES:!aNULL no-sslv3 Note: and will be different for each frontend. If the ciphers listed are not as shown above, this is a finding.

Fix Text (F-43233r665291_fix)
Navigate to and open the following files: /etc/haproxy/conf.d/20-vcac.cfg /etc/haproxy/conf.d/30-vro-config.cfg Configure the bind option for each frontend with the following ciphers parameter: 'ciphers FIPS:+3DES:!aNULL'.